<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sway on Today I learned…</title>
    <link>https://alex.dandrea.io/tags/sway/</link>
    <description>Recent content in Sway on Today I learned…</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 21 Dec 2024 13:55:00 +0100</lastBuildDate>
    <atom:link href="https://alex.dandrea.io/tags/sway/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Interactive Brokers&#39; Trader Workstation on Wayland</title>
      <link>https://alex.dandrea.io/2024/12/21/interactive-brokers-trading-workstation-on-wayland/</link>
      <pubDate>Sat, 21 Dec 2024 12:14:00 +0100</pubDate>
      <guid>https://alex.dandrea.io/2024/12/21/interactive-brokers-trading-workstation-on-wayland/</guid>
      <description>I need to run Interactive Brokers Trader Workstation on Linux on Wayland on HiDPI - a fateful combination</description>
    </item>
    <item>
      <title>Fixing idle-inhibitor behaviour in Firefox with Wayland</title>
      <link>https://alex.dandrea.io/2024/07/20/fixing-idle-inhibitor-behaviour-in-firefox-with-wayland/</link>
      <pubDate>Sat, 20 Jul 2024 17:44:21 +0200</pubDate>
      <guid>https://alex.dandrea.io/2024/07/20/fixing-idle-inhibitor-behaviour-in-firefox-with-wayland/</guid>
      <description>&lt;p&gt;Whenever Firefox played videos or - actually more relevant - I watched the shared screen of a colleague, after some time the screenlock would start. This is especially annoying, since I have to enter my password to unlock again.&lt;/p&gt;&#xA;&lt;p&gt;In my status way &lt;em&gt;waybar&lt;/em&gt; there is an idle inhibit switch which I could then use to prevent the lock from activating. That this switch worked led to the conclusion that there is something with Firefox that prevented this from working. Behind the scenes, there are two components that have mixed responsibility when it comes to locking / suspending / sleeping - responsibilities which overlap, and are not completely clear in the end.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Archlinux Sway with a 4K display</title>
      <link>https://alex.dandrea.io/2023/12/20/archlinux-sway-with-a-4k-display/</link>
      <pubDate>Wed, 20 Dec 2023 16:12:36 +0100</pubDate>
      <guid>https://alex.dandrea.io/2023/12/20/archlinux-sway-with-a-4k-display/</guid>
      <description>Subtle issues running an external 4K display on Linux</description>
    </item>
    <item>
      <title>Managing Sway tools as systemd services</title>
      <link>https://alex.dandrea.io/2023/10/27/managing-sway-tools-as-systemd-services/</link>
      <pubDate>Fri, 27 Oct 2023 00:00:00 +0000</pubDate>
      <guid>https://alex.dandrea.io/2023/10/27/managing-sway-tools-as-systemd-services/</guid>
      <description>&lt;p&gt;I recently took some time to set up some of the accompanying services of Sway (the window manager) as systemd user services. Those services are &lt;code&gt;dunst&lt;/code&gt;, &lt;code&gt;blueman-applet&lt;/code&gt;, &lt;code&gt;kanshi&lt;/code&gt; - amongst others.&lt;/p&gt;&#xA;&lt;p&gt;The most simple way to run those applications are to &lt;code&gt;exec&lt;/code&gt; them when Sway starts. This is simple, but it lacks everything from automatic restart, reloading configuration and status inspection.&lt;/p&gt;&#xA;&lt;p&gt;So, let&amp;rsquo;s look at &lt;code&gt;kanshi&lt;/code&gt;, the service that magically manages different monitors that get detected on the system at any time; you&amp;rsquo;d run it within sway as:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Waiting for Waybar tray</title>
      <link>https://alex.dandrea.io/2023/09/09/waiting-for-waybar-tray/</link>
      <pubDate>Sat, 09 Sep 2023 00:00:00 +0000</pubDate>
      <guid>https://alex.dandrea.io/2023/09/09/waiting-for-waybar-tray/</guid>
      <description>&lt;p&gt;When starting &lt;a href=&#34;https://github.com/swaywm/sway&#34;&gt;sway&lt;/a&gt;, it takes a while until &lt;a href=&#34;https://github.com/Alexays/Waybar&#34;&gt;waybar&lt;/a&gt; has fully started. A possible speed up trick has been documented in &lt;a href=&#34;https://github.com/swaywm/sway/wiki#gtk-applications-take-20-seconds-to-start&#34;&gt;sway GitHub&lt;/a&gt;, but it&amp;rsquo;s still delayed from time to time.&lt;/p&gt;&#xA;&lt;p&gt;The problem is though, that some applications that embed into the system tray which is provided by waybar cannot register themselves in such a case. One part of apps managed to &amp;rsquo;late register&amp;rsquo; once waybar&amp;rsquo;s systray then becomes available, but others do not. Examples for the latter are KeepassXC and OnedriveGUI.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
